bookmark: Add git remote origin hint - #10070
Open
barun511 wants to merge 1 commit into
Open
Conversation
Contributor
|
Please move the PR description into the commit message, since the project reviews individual commits. |
Adds a hint to the `jj bookmark track` command if the remote specified was unmatched - so that the user knows how to add the remote.
Author
|
Thank you! I added a description to the commit message |
Contributor
|
I don't think it's a common mistake to run |
Contributor
|
I generally like the idea of making the error messages as helpful as possible, but I think this might lead to some false positives.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When setting up a new repo, I had to look up this command - figured it could just be a jj hint instead!
Before:
After:

Checklist
If applicable:
CHANGELOG.mdREADME.md,docs/,demos/)cli/src/config-schema.json)how it works, how it's organized), including any code drafted by an LLM.
an eye towards deleting anything that is irrelevant, clarifying anything
that is confusing, and adding details that are relevant. This includes,
for example, commit descriptions, PR descriptions, and code comments.